Release 10.1A: OpenEdge Application Server:
Developing AppServer Applications

Understanding the scope of persistent procedures

A remote procedure on the AppServer that you run with the PERSISTENT option, and a local procedure that you run with the PERSISTENT option both perform in identical fashion. That is, its context is created when the instantiating procedure starts to execute and that context persists after it returns until the end of the Progress 4GL session, or until it is explicitly deleted.

When a remote procedure is run persistently, the persistent context is managed strictly within the AppServer session where the persistent procedure is run. This is consistent with the existence of the processing boundary that separates an AppServer session distinctly from a client application session. If a remote procedure creates other local Progress 4GL objects (persistent procedures), these objects are only available locally within the AppServer agent in which they were created. These objects cannot be shared between a Progress 4GL client application and the AppServer session.